Skip to main content

Custom Datasets in Corva Traces App

Introduction​

Corva has a feature in the Traces Drilling app where a developer can create and populate data in a custom datasets and visualize the data in the application.


How is a dataset populated for use in the Traces application?​

  1. The first way is to build a backend app in either Python or Node.js, then post data to the custom dataset.

  2. The second way is to post to the custom dataset from an external app or platform via Corva’s API and an API Key.

image|466x72

Image of Data Flow Chart


What are the dataset requirements for using custom curves in the Traces app?​

  1. The dataset must be TIME indexed.

NOTE: The developer will select a time based dataset when creating the dataset in the dataset wizard or when creating a backend app in the app wizard.

image|466x72

Image of Selecting a Time Based Dataset

  1. Must have a consistent time interval between timestamps. Time intervals can be any interval e.g. 1 second or 1 minute or 10 minute intervals, as long as they are consistent.

  2. The customer dataset must be marked as “Plottable” by a Corva Dev Advocate. This is an administrative task that the developer can request from the Corva Dev Advocate via Support Ticket. The Dev Advocate will review the dataset to confirm that the dataset meets all the requirements.

  3. All dataset fields that you would like to be rendered in the Traces app must be present in the very first record of the dataset. The reason for this is that Corva's Traces app conducts an initial fetch of the dataset fields from the very first record of the custom dataset, then renders in a dropdown menu for users to select in the Traces app.

image|466x72